Pre-emption During CSI-RS Mobility Measurements

ABSTRACT

A base station communicates with a first user equipment (UE) and a second UE. The base station determines a first configuration for the first UE for a channel state information reference signal (CSI-RS) on a symbol, schedules a data transmission for the second UE on the symbol where the CSI-RS is configured so that the CSI-RS and the data transmission collide on the symbol and determines a second configuration for the first UE when the CSI-RS and the data transmission collide on the symbol.

PRIORITY CLAIM/INCORPORATION BY REFERENCE

This application claims priority to U.S. Provisional Application Ser.No. 63/028,323 filed May 21, 2020 and entitled “Pre-emption DuringCSI-RS Mobility Measurements,” the entirety of which is incorporated byreference herein.

BACKGROUND INFORMATION

A channel state information reference symbol (CSI-RS) may be configuredby a 5G New Radio (NR) network for a user equipment (UE) to performmobility measurements. The UE may monitor downlink channels for CSI-RStransmissions from the network in accordance with resource locationsidentified by the CSI-RS configuration. When the CSI-RS transmission isreceived, the UE may generate channel quality information (CQI) for aserving cell and/or one or more neighbor cells, for example, for layer-3(L3) mobility management.

Pre-emption relates to a prioritization of data traffic for particularapplications requiring fast and reliable data transmissions, such aspublic safety applications. For example, in 5G NR, a UE in an enhancedmobile broadband (eMBB) configuration may have eMBB services preemptedby ultra-reliable low latency communication (URLLC) services. Apre-emption indication may be transmitted to the UE and the UE mayassume that no transmissions to the UE are present in physical resourceblocks (PRBs) and OFDM symbols indicated by the pre-emption bits.However, the UE behavior for mobility measurements may be unclear whenthe OFDM symbols indicated by the pre-emption bits collide with CSI-RStransmissions for the UE.

SUMMARY

Some exemplary embodiments are related to a processor of a base stationthat is communicating with a first user equipment (UE) and a second UEand is configured to perform operations. The operations includedetermining a first configuration for the first UE for a channel stateinformation reference signal (CSI-RS) on a symbol, scheduling a datatransmission for the second UE on the symbol where the CSI-RS isconfigured so that the CSI-RS and the data transmission collide on thesymbol and determining a second configuration for the first UE when theCSI-RS and the data transmission collide on the symbol.

Other exemplary embodiments are related to a processor of a first basestation that is communicating with a first user equipment (UE) and asecond UE and is configured to perform operations. The operationsinclude exchanging timing information with a second base station,determining if a channel state information reference signal (CSI-RS)configured for the first UE for measuring CSI on the second base stationcollides with a data transmission for the second UE on a same symbol xand configuring a zero-power CSI-RS (ZP-CSI-RS) as the CSI-RS for thefirst UE CSI measurement on the second base station.

Still further exemplary embodiments are related to a processor of afirst base station that is communicating with a first user equipment(UE) and a second UE and is configured to perform operations. Theoperations include configuring the second UE for a data transmission onsymbol x and transmitting a pre-emption indication to the first UE onsymbol x, wherein the pre-emption indication configures the first UE tonot decode a physical downlink shared channel (PDSCH) on the symbol xand, when a channel state information reference signal (CSI-RS) isconfigured for the first UE for measuring CSI from a second base stationon symbol x, the first UE performs the CSI measurement on the symbol x.

Additional exemplary embodiments are related to a processor of a basestation that is communicating with a first user equipment (UE) and asecond UE and is configured to perform operations. The operationsinclude determining a first configuration for the first UE for a specialphysical downlink shared channel (PDSCH) on a symbol, scheduling a datatransmission for the second UE on the symbol where the special PDSCH isconfigured so that the special PDSCH and the data transmission collideand transmitting a pre-emption indication to the first UE for thesymbol, wherein the first UE ignores the pre-emption indication anddecodes the special PDSCH.

Further exemplary embodiments are related to a processor of a basestation that is communicating with a first user equipment (UE) in anultra reliable low latency communications (URLLC) configuration and asecond UE and is configured to perform operations. The operationsinclude determining a configuration for the first UE for a specialphysical downlink shared channel (PDSCH) on a symbol and scheduling adata transmission for the second UE on the symbol where the specialPDSCH is configured so that the special PDSCH and the data transmissioncollide, wherein the second UE ignores the data transmission and decodesthe PDSCH.

Still other exemplary embodiments are related to a processor of a basestation that is communicating with a user equipment (UE) in an ultrareliable low latency communications (URLLC) configuration and isconfigured to perform operations. The operations include determining aconfiguration for the UE for mobility downlink (DL) measurements of thebase station or one or more neighbor base stations on a symbol andscheduling a data transmission for the UE on the symbol where thespecial PDSCH is configured so that the special PDSCH and the datatransmission collide, wherein the UE prioritizes decoding the datatransmission over the mobility DL measurements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a network arrangement according to various exemplaryembodiments.

FIG. 2 shows an exemplary UE according to various exemplary embodiments.

FIG. 3 shows an exemplary network base station according to variousexemplary embodiments.

FIG. 4 shows a method for a UE in an enhanced mobile broadband (eMBB)configuration to perform mobility measurements according to variousexemplary embodiments.

FIG. 5 shows a first network configuration for performing L3 CSI-RSneighbor cell measurements according to various exemplary embodiments.

FIG. 6 shows a second network configuration for performing L3 CSI-RSneighbor cell measurements according to various exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments may be further understood with reference tothe following description and the related appended drawings, whereinlike elements are provided with the same reference numerals. Theexemplary embodiments describe network configurations for a userequipment (UE) to manage scenarios where mobility measurement referencesignals, e.g., channel state information reference signals (CSI-RS), mayconflict/collide with high priority data, e.g. URLLC data transmissions.

FIG. 1 shows an exemplary network arrangement 100 according to variousexemplary embodiments. The exemplary network arrangement 100 includes aplurality of UEs 110, 112. Those skilled in the art will understand thatthe UEs may be any type of electronic component that is configured tocommunicate via a network, e.g., a component of a connected car, amobile phone, a tablet computer, a smartphone, a phablet, an embeddeddevice, a wearable, an Internet of Things (IoT) device, etc. It shouldalso be understood that an actual network arrangement may include anynumber of UEs being used by any number of users. Thus, the example oftwo UEs 110, 112 is merely provided for illustrative purposes. In someof the exemplary embodiments described below, groups of UEs may beemployed to conduct respective channel measurements.

The UEs 110, 112 may communicate directly with one or more networks. Inthe example of the network configuration 100, the networks with whichthe UEs 110, 112 may wirelessly communicate are a 5G NR radio accessnetwork (5G NR-RAN) 120, an LTE radio access network (LTE-RAN) 122 and awireless local access network (WLAN) 124. Therefore, the UEs 110, 112may include a 5G NR chipset to communicate with the 5G NR-RAN 120, anLTE chipset to communicate with the LTE-RAN 122 and an ISM chipset tocommunicate with the WLAN 124. However, the UEs 110, 112 may alsocommunicate with other types of networks (e.g. legacy cellular networks)and the UE 110 may also communicate with networks over a wiredconnection. With regard to the exemplary embodiments, the UEs 110, 112may establish a connection with the 5G NR-RAN 122. The connections maybe either one of an enhanced mobile broadband (eMBB) connection or anultra-reliable low latency communications (URLLC) connection.

The 5G NR-RAN 120 and the LTE-RAN 122 may be portions of cellularnetworks that may be deployed by cellular providers (e.g., Verizon,AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example,cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs,macrocells, microcells, small cells, femtocells, etc.) that areconfigured to send and receive traffic from UEs that are equipped withthe appropriate cellular chip set. The WLAN 124 may include any type ofwireless local area network (WiFi, Hot Spot, IEEE 802.11x networks,etc.).

The UEs 110, 112 may connect to the 5G NR-RAN via at least one of thenext generation nodeB (gNB) 120A and/or the gNB 120B. The gNBs 120A,120B may be configured with the necessary hardware (e.g., antennaarray), software and/or firmware to perform massive multiple in multipleout (MIMO) functionality. Massive MIMO may refer to a base station thatis configured to generate a plurality of beams for a plurality of UEs.Reference to two gNB 120A, 120B is merely for illustrative purposes. Theexemplary embodiments may apply to any appropriate number of gNBs. TheUEs 110, 112 may also connect to the LTE-RAN 122 via either or both ofthe eNBs 122A, 122B, or to any other type of RAN, as mentioned above.

In the network arrangement 100, the UEs 110, 112 are shown as havingconnections to the gNB 120A. In some embodiments, the UE 110 may beconnected to the gNB 120A via an eMBB connection while the UE 112 may beconnected to the gNB 120A via a URLLC connection. The gNB 120A maytransmit a pre-emption indication to the eMBB UE, e.g., UE 110, so thata URLLC data transmission may be sent to the URLLC UE e.g., UE 112, onthe pre-emption symbols with little to no interference being caused bytransmissions over the eMBB connection. The pre-emption indication maybe a Downlink Control Information (DCI) signal, e.g., DCI Format 2_1.The gNB 120B may be a neighbor cell to the gNB 120A and be used forchannel state information (CSI) measurements, as described in furtherdetail below.

In addition to the networks 120, 122 and 124 the network arrangement 100also includes a cellular core network 130, the Internet 140, an IPMultimedia Subsystem (IMS) 150, and a network services backbone 160. Thecellular core network 130 may be considered to be the interconnected setof components that manages the operation and traffic of the cellularnetwork. The cellular core network 130 also manages the traffic thatflows between the cellular network and the Internet 140. The IMS 150 maybe generally described as an architecture for delivering multimediaservices to the UE 110 using the IP protocol. The IMS 150 maycommunicate with the cellular core network 130 and the Internet 140 toprovide the multimedia services to the UE 110. The network servicesbackbone 160 is in communication either directly or indirectly with theInternet 140 and the cellular core network 130. The network servicesbackbone 160 may be generally described as a set of components (e.g.,servers, network storage arrangements, etc.) that implement a suite ofservices that may be used to extend the functionalities of the UE 110 incommunication with the various networks.

FIG. 2 shows an exemplary UE 110 according to various exemplaryembodiments. The UE 110 will be described with regard to the networkarrangement 100 of FIG. 1. The UE 110 may represent any electronicdevice and may include a processor 205, a memory arrangement 210, adisplay device 215, an input/output (I/O) device 220, a transceiver 225,and other components 230. The other components 230 may include, forexample, an audio input device, an audio output device, a battery thatprovides a limited power supply, a data acquisition device, ports toelectrically connect the UE 110 to other electronic devices, sensors todetect conditions of the UE 110, etc. The UE 110 illustrated in FIG. 2may also represent the UE 112.

The processor 205 may be configured to execute a plurality of enginesfor the UE 110. For example, the engines may include a CSI engine 235.The CSI engine 235 may perform operations including performing channelmeasurements, e.g., for a CSI-RS based on a network configuration thataccounts for potential collisions with URLLC data transmissions.

The above referenced engine being an application (e.g., a program)executed by the processor 205 is only exemplary. The functionalityassociated with the engines may also be represented as a separateincorporated component of the UE 110 or may be a modular componentcoupled to the UE 110, e.g., an integrated circuit with or withoutfirmware. For example, the integrated circuit may include inputcircuitry to receive signals and processing circuitry to process thesignals and other information. The engines may also be embodied as oneapplication or separate applications. In addition, in some UEs, thefunctionality described for the processor 205 is split among two or moreprocessors such as a baseband processor and an applications processor.The exemplary embodiments may be implemented in any of these or otherconfigurations of a UE.

The memory 210 may be a hardware component configured to store datarelated to operations performed by the UE 110. The display device 215may be a hardware component configured to show data to a user while theI/O device 220 may be a hardware component that enables the user toenter inputs. The display device 215 and the I/O device 220 may beseparate components or integrated together such as a touchscreen. Thetransceiver 225 may be a hardware component configured to establish aconnection with the 5G-NR RAN 120, the LTE RAN 122 etc. Accordingly, thetransceiver 225 may operate on a variety of different frequencies orchannels (e.g., set of consecutive frequencies).

FIG. 3 shows an exemplary network base station, in this case gNB 120A,according to various exemplary embodiments. As noted above with regardto the UE 110, the gNB 120A may represent a base station providingservices to the UE 110. The gNB 120A may represent any access node ofthe 5G NR network through which the UEs 110, 112 may establish aconnection and manage network operations. The gNB 120A illustrated inFIG. 3 may also represent the gNB 120B.

The gNB 120A may include a processor 305, a memory arrangement 310, aninput/output (I/O) device 320, a transceiver 325, and other components330. The other components 330 may include, for example, an audio inputdevice, an audio output device, a battery, a data acquisition device,ports to electrically connect the gNB 120A to other electronic devices,etc.

The processor 305 may be configured to execute a plurality of engines ofthe gNB 120A. For example, the engines may include a CSI managementengine 335 and a URLLC data management engine 340. The CSI managementengine 335 may perform operations including configuring a UE to performchannel measurements in view of potential collisions with URLLC datatransmissions. The URLLC data management engine 340 may performoperations including configuring a UE for URLLC data transmissions.

The above noted engines each being an application (e.g., a program)executed by the processor 305 is only exemplary. The functionalityassociated with the engines may also be represented as a separateincorporated component of the gNB 120A or may be a modular componentcoupled to the gNB 120A, e.g., an integrated circuit with or withoutfirmware. For example, the integrated circuit may include inputcircuitry to receive signals and processing circuitry to process thesignals and other information. In addition, in some gNBs, thefunctionality described for the processor 305 is split among a pluralityof processors (e.g., a baseband processor, an applications processor,etc.). The exemplary embodiments may be implemented in any of these orother configurations of a gNB.

The memory 310 may be a hardware component configured to store datarelated to operations performed by the UEs 110, 112. The I/O device 320may be a hardware component or ports that enable a user to interact withthe gNB 120A. The transceiver 325 may be a hardware component configuredto exchange data with the UEs 110, 112 and any other UE in the system100. The transceiver 325 may operate on a variety of differentfrequencies or channels (e.g., set of consecutive frequencies).

Preemption relates to a prioritization of data traffic for particularapplications requiring fast and reliable data transmissions, such aspublic safety applications. In 5G NR, a UE in an enhanced mobilebroadband (eMBB) configuration may have eMBB services preempted byultra-reliable low latency communication (URLLC) services.

In the Third Generation Partnership (3GPP) Technical Specification TS38.212, the DCI Format 2_1 is defined for 5G NR. The DCI Format 2_1 maybe used for notifying a UE of physical resource block(s) (PRBs) and OFDMsymbol(s) where the UE may assume no transmission is intended for theUE. The following information may be transmitted by means of the DCIformat 2_1 with a cyclic redundancy check (CRC) scrambled by anINT-RNTI: Pre-emption indication 1, Pre-emption indication 2, . . . ,Pre-emption indication N. The size of DCI format 2_1 is configurable byhigher layers up to 126 bits (according to Clause 11.2 of [5, TS38.213]). Each pre-emption indication is 14 bits.

The UE behavior when it receives a DCI Format 2_1 may be as follows. Ifa UE detects a DCI format 2_1 for a serving cell from the configured setof serving cells, the UE may assume that no transmissions to the UE arepresent in PRBs and in symbols that are indicated by the DCI format 2_1,from a set of PRBs and a set of symbols of the last monitoring period.The indication by the DCI format 2_1 is not applicable to receptions ofSS/PBCH blocks. In the example started above, when the eMBB UE (e.g., UE110) receives the DCI format 2_1, the UE 110 will understand that thereis no transmission to the UE 110 in the indicated symbols. Thus, the UE110 may not monitor these symbols because there will be no transmissionsfor the UE 110.

A CSI-RS may be configured for the UE for performing mobilitymeasurements. The UE may monitor downlink channels for CSI-RStransmissions from the network in accordance with resource locationsidentified by the CSI-RS configuration. When the CSI-RS transmission isreceived, the UE may generate channel quality information (CQI) for aserving cell and/or one or more neighbor cells, for example for layer-3(L3) mobility management. However, there is a potential for CSI-RStransmissions to collide with the OFDM symbols indicated by thepre-emption bits. If the UE 110 is not monitoring these symbols, the UE110 will not receive and measure the CSI-RS for mobility and/or anyother purpose.

According to some exemplary embodiments, the network configures URLLCdata transmissions and/or L3 CSI-RSs for serving cell measurements foran eMBB UE so that collisions between the OFDM symbols in a pre-emptionindication and the CSI-RS may be avoided and/or managed.

According to other exemplary embodiments, the network may schedule URLLCdata for a URLLC UE on the symbols where an L3 CSI-RS measurement isconfigured for an eMBB UE. The following provides several exemplarymanners of handling this scenario.

In some exemplary embodiments, the network avoids indicating pre-emptionto the eMBB UE for those symbols with L3 CSI-RSs configured. In otherwords, although the URLLC data and the L3 CSI-RS may collide, the eMBBUE will not receive a pre-emption indication for those symbols and stillperforms channel measurements despite the channel being additionallyused for the URLLC data.

In other exemplary embodiments, the network configures a zero-powerCSI-RS (ZP-CSI-RS) to be the L3 CSI-RS measurement for the eMBB UE,regardless of a pre-emption configuration. A ZP-CSI-RS masks or mutescertain resource elements (REs) to make those REs unavailable forPhysical Downlink Scheduling Channel (PDSCH) transmission to allow foran interference measurement. A ZP-CSI-RS does not mean that there is notransmission in the resource element. Rather, the resource elementincludes a non-zero power CSI-RS (NZP-CSI-RS) for the other UE, e.g., UE112 in the current example. In this exemplary embodiment, since theZP-CSI-RS is configured for the L3 CSI-RS measurement, the URLLC UE andthe eMBB UE will skip those CSI-RS symbols for data reception and onlyuse the symbols for interference and mobility measurements.

In still further exemplary embodiments, the network may apply ascheduling restriction for all connected UEs, including the URLLC UE andthe eMBB UE, on CSI-RS symbols for L3 measurement. For example, thenetwork may not schedule CSI-RS symbols for L3 measurements for certainsymbols. As opposed to the above exemplary embodiments where the networkwill not schedule URLLC data transmissions and/or L3 CSI-RSs toconflict, in these exemplary embodiments, there may be instances whenthere is a conflict, but there may be certain symbols where schedulingrestrictions will eliminate the conflicts by not scheduling the CSI-RSsymbols for L3 measurements in certain symbols. In these exemplaryembodiments, the URLLC and eMBB UEs will expect a scheduling restrictionon CSI-RS symbols for L3 measurements.

FIG. 4 shows a method 400 for a UE in an enhanced mobile broadband(eMBB) configuration to perform mobility measurements. In 405, the UEreceives a first network configuration for a CSI-RS. In 410, the networkschedules URLLC data for a URLLC UE on the symbols where an L3 CSI-RSmeasurement is configured. As discussed above, in this example, theURLLC data and the CSI-RS may collide.

In 415, the network determines a second configuration for the eMBB UE inview of the collision between the URLLC data and the CSI-RS. Asdiscussed above, in some exemplary embodiments, the network will notindicate any pre-emption for those symbols to the eMBB UE. Thus, thesecond configuration will remain the same as the first configuration forthe eMBB UE. In other exemplary embodiments, the second configurationcomprises a ZP-CSI-RS for the L3 CSI-RS regardless of whether the UEreceives a pre-emption indication. In still further exemplaryembodiments, the network applies the scheduling restriction discussedabove.

The above exemplary embodiments addressed issues related to pre-emptionwith respect to CSI-RS measurements for a serving cell. The followingexemplary embodiments address issues related to CSI-RS measurements forneighbor cells. According to the following exemplary embodiments, thenetwork configures URLLC data transmissions and/or L3 CSI-RSs forneighbor cell measurements for an eMBB UE so that collisions between theOFDM symbols in a pre-emption indication and the CSI-RS may be avoidedand/or managed.

FIG. 5 shows a first network configuration 500 for performing L3 CSI-RSneighbor cell measurements according to various exemplary embodiments.In this exemplary embodiment, a first (serving) cell gNB 120A is in ascenario with an eMBB connection established with a first UE 110 and aURLLC connection established with a second UE 112. The gNB 120B is aneighbor cell.

In signal 505, the serving cell gNB 120A, exchanges timing informationwith the neighbor cell gNB 120B. In view of the timing information, thegNB 120A determines if the CSI-RS L3 measurement for the eMBB UE 110 onthe neighbor cell (signal 510) collides with a URLLC data symbol for theURLLC UE 112 on the first cell gNB 120A (signal 515).

If the URLLC data channel of the serving cell gNB 120A collides with theCSI-RS on symbol x of the neighbor cell gNB 120B, the serving cell gNB120A configures a ZP-CSI-RS for the eMBB UE 110 on symbols x−1, x andx+1 to perform the CSI-RS L3 neighbor cell measurements. The servingcell gNB 120A will avoid scheduling any PDSCH on those ZP-CSI-RS symbolsx−1, x and x+1. While the serving cell gNB 120A and the neighbor cellgNB 120B may exchange timing information, there still may be a cellphase synchronization misalignment between the cells. This is why theserving cell gNB 120A will configure the symbols x−1, x and x+1 with theZP-CSI-RS rather than just the symbol x. However, it should beunderstood that other combinations of symbols may be configured asZP-CSI-RS depending on the accuracy of the timing information andalignment.

The eMBB UE 110 will not decode any PDSCH on the ZP-CSI-RS symbols x−1,x and x+1 indicated by the serving cell gNB 120A, and instead willperform the CSI-RS L3 measurement for the neighbor cell gNB 120B onthose symbols.

FIG. 6 shows a second network configuration 600 for performing L3 CSI-RSneighbor cell measurements according to various exemplary embodiments.In this exemplary embodiment, a first (serving) cell gNB 120A is in ascenario with an eMBB connection established with a first UE 110 and aURLLC connection established with a second UE 112. The gNB 120B is aneighbor cell.

In this exemplary embodiment, the serving cell gNB 120A indicates to theeMBB UE 110, a pre-emption indication on symbol x (signal 605). Thepre-emption indication corresponds to the OFDM symbols scheduled tocarry URLLC data on symbol x (signal 610) to the URLLC 112. The UE 110will not decode any PDSCH on symbol x based on the pre-emptionindication. If the CSI-RS for neighbor cell measurements happens to betransmitted on symbol x (signal 615), the eMBB UE 110 will measure theCSI-RS from the second cell gNB 120B.

In other exemplary embodiments, the network may schedule URLLC datatransmissions and/or special PDSCH that collide. For example, a specialPDSCH may comprise a Remaining Minimum System Information (RMSI) with asystem information update for the eMBB UE. In this scenario, theexemplary embodiments may be implemented so that collisions between theOFDM symbols in a pre-emption indication and the special PDSCH may beavoided and/or managed.

According to some exemplary embodiments, the network avoids configuringpre-emption on the symbols carrying a special PDSCH, e.g., an RMSIPDSCH, or another PDSCH carrying system information. The network willavoid scheduling URLLC data that will collide with those special PDSCHon the same frequency/time domain resource.

In other exemplary embodiments, the network may schedule URLLC data fora URLLC UE on the symbols carrying a special PDSCH. In these scenarioswhen the network configures pre-emption that collides with the specialPDSCH, the UE ignores the pre-emption indication to decode the specialPDSCH. For example, an eMBB UE will ignore pre-emption to keep decodingthe special PDSCH. In another example, a URLLC UE will ignore the URLLCdata but decode the special PDSCH.

According to still further exemplary embodiments, the network mayconfigure URLLC data transmissions and/or URLLC DL measurements for aURLLC UE that collide. The exemplary embodiments may be implemented sothat collisions between the data channel and the DL measurement may beavoided and/or managed.

In some exemplary embodiments, a measurement restriction may be appliedon URLLC data symbols for the URLLC UE. The URLLC UE may prioritizedecoding the URLLC data channel rather than the mobility DL measurementof neighbor cells and/or the serving cell. For example, the URLLC UE mayprioritize decoding the URLLC data channel rather than the Radio LinkMonitoring (RLM), Beam Failure Detection (BFD), Candidate Beam Detection(CBD) and Layer 1 Reference Signal Received Power (L1 RSRP) measurementsof the serving cell.

In other exemplary embodiments, timing information may be exchangedbetween serving and neighbor cells. Based on this timing information,the network may avoid configuring the URLLC UE to perform measurementson those URLLC data symbols that collide with the URLLC datatransmissions.

In still further exemplary embodiments, timing information may again beexchanged between serving and neighbor cells. Based on this timinginformation, the network may avoid scheduling the URLLC data channelthat collide with the URLLC DL measurements.

Examples

A first example includes a processor of a first base station that iscommunicating with a first user equipment (UE) and a second UE and isconfigured to perform operations comprising exchanging timinginformation with a second base station, determining if a channel stateinformation reference signal (CSI-RS) configured for the first UE formeasuring CSI on the second base station collides with a datatransmission for the second UE on a same symbol x and configuring azero-power CSI-RS (ZP-CSI-RS) as the CSI-RS for the first UE CSImeasurement on the second base station.

A second example includes the processor of the first example, whereinthe first UE is in an enhanced mobile broadband (eMBB) configurationwith the first base station and the second UE is in an ultra reliablelow latency communications (URLLC) configuration with the first basestation.

A third example includes the processor of the second example, whereinthe ZP-CSI-RS is configured on the symbol x, symbol x−1, and symbol x+1.

A fourth example includes the processor of the third example, whereinthe operations further comprise configuring the first UE to not decodeany physical downlink shared channel (PDSCH) on the symbols x−1, x andx+1.

A fifth example includes a processor of a first base station that iscommunicating with a first user equipment (UE) and a second UE and isconfigured to perform operations comprising configuring the second UEfor a data transmission on symbol x and transmitting a pre-emptionindication to the first UE on symbol x, wherein the pre-emptionindication configures the first UE to not decode a physical downlinkshared channel (PDSCH) on the symbol x and, when a channel stateinformation reference signal (CSI-RS) is configured for the first UE formeasuring CSI from a second base station on symbol x, the first UEperforms the CSI measurement on the symbol x.

A sixth example includes the processor of the fifth example, wherein thefirst UE is in an enhanced mobile broadband (eMBB) configuration withthe first base station and the second UE is in an ultra reliable lowlatency communications (URLLC) configuration with the first basestation.

A seventh example includes a processor of a base station that iscommunicating with a first user equipment (UE) and a second UE and isconfigured to perform operations comprising determining a firstconfiguration for the first UE for a special physical downlink sharedchannel (PDSCH) on a symbol, scheduling a data transmission for thesecond UE on the symbol where the special PDSCH is configured so thatthe special PDSCH and the data transmission collide and transmitting apre-emption indication to the first UE for the symbol, wherein the firstUE ignores the pre-emption indication and decodes the special PDSCH.

An eighth example includes the processor of the seventh example, whereinthe first UE is in an enhanced mobile broadband (eMBB) configurationwith the base station and the second UE is in an ultra reliable lowlatency communications (URLLC) configuration with the base station.

A ninth example includes the processor of the seventh example, whereinthe special PDSCH is a remaining minimum system information (RMSI).

A tenth example includes a base station that is communicating with afirst user equipment (UE) in an ultra reliable low latencycommunications (URLLC) configuration and a second UE and is configuredto perform operations comprising determining a configuration for thefirst UE for a special physical downlink shared channel (PDSCH) on asymbol and scheduling a data transmission for the second UE on thesymbol where the special PDSCH is configured so that the special PDSCHand the data transmission collide, wherein the second UE ignores thedata transmission and decodes the PDSCH.

An eleventh example includes a base station that is communicating with auser equipment (UE) in an ultra reliable low latency communications(URLLC) configuration and is configured to perform operations comprisingdetermining a configuration for the UE for mobility downlink (DL)measurements of the base station or one or more neighbor base stationson a symbol and scheduling a data transmission for the UE on the symbolwhere the special PDSCH is configured so that the special PDSCH and thedata transmission collide, wherein the UE prioritizes decoding the datatransmission over the mobility DL measurements.

A twelfth example includes the processor of the eleventh example,wherein the mobility DL measurements comprise one of a Radio LinkMonitoring (RLM), Beam Failure Detection (BFD), Candidate Beam Detection(CBD) and Layer 1 Reference Signal Received Power (L1 RSRP) measurementsof the serving cell.

Those skilled in the art will understand that the above-describedexemplary embodiments may be implemented in any suitable software orhardware configuration or combination thereof. An exemplary hardwareplatform for implementing the exemplary embodiments may include, forexample, an Intel x86 based platform with compatible operating system, aWindows OS, a Mac platform and MAC OS, a mobile device having anoperating system such as iOS, Android, etc. In a further example, theexemplary embodiments of the above described method may be embodied as aprogram containing lines of code stored on a non-transitory computerreadable storage medium that, when compiled, may be executed on aprocessor or microprocessor.

Although this application described various embodiments each havingdifferent features in various combinations, those skilled in the artwill understand that any of the features of one embodiment may becombined with the features of the other embodiments in any manner notspecifically disclaimed or which is not functionally or logicallyinconsistent with the operation of the device or the stated functions ofthe disclosed embodiments.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

It will be apparent to those skilled in the art that variousmodifications may be made in the present disclosure, without departingfrom the spirit or the scope of the disclosure. Thus, it is intendedthat the present disclosure cover modifications and variations of thisdisclosure provided they come within the scope of the appended claimsand their equivalent.

1. A processor of a base station that is communicating with a first userequipment (UE) and a second UE and is configured to perform operationscomprising: determining a first configuration for the first UE for achannel state information reference signal (CSI-RS) on a symbol;scheduling a data transmission for the second UE on the symbol where theCSI-RS is configured so that the CSI-RS and the data transmissioncollide on the symbol; and determining a second configuration for thefirst UE when the CSI-RS and the data transmission collide on thesymbol.
 2. The processor of claim 1, wherein the first UE is in anenhanced mobile broadband (eMBB) configuration with the base station andthe second UE is in an ultra reliable low latency communications (URLLC)configuration with the base station.
 3. The processor of claim 2,wherein the CSI-RS is used by the first UE to perform layer 3 (L3)CSI-RS mobility measurements.
 4. The processor of claim 3, wherein thebase station does not indicate pre-emption to the first UE and thesecond configuration is the first configuration.
 5. The processor ofclaim 3, wherein the second configuration includes a zero-power CSI-RS(ZP-CSI-RS) as the L3 CSI-RS.
 6. The processor of claim 3, wherein theoperations further comprise: applying a scheduling restriction to thefirst UE on the symbol.
 7. The processor of claim 6, wherein thescheduling restriction comprises not scheduling control or datatransmissions to the first UE on the symbol.
 8. The processor of claim7, wherein the not scheduling the data transmissions comprises notscheduling Physical Downlink Control Channel (PDSCH) transmissions. 9.The processor of claim 6, wherein the operations further comprise:applying a scheduling restriction to the second UE on the symbol.
 10. Abase station, comprising: a transceiver configured to communicate with afirst user equipment (UE) and a second UE; and a processorcommunicatively coupled to the transceiver and configured to performoperations comprising: determining a first configuration for the firstUE for a channel state information reference signal (CSI-RS) on asymbol; scheduling a data transmission for the second UE on the symbolwhere the CSI-RS is configured so that the CSI-RS and the datatransmission collide on the symbol; and determining a secondconfiguration for the first UE when the CSI-RS and the data transmissioncollide on the symbol.
 11. The base station of claim 10, wherein thefirst UE is in an enhanced mobile broadband (eMBB) configuration withthe base station and the second UE is in an ultra reliable low latencycommunications (URLLC) configuration with the base station.
 12. The basestation of claim 11, wherein the CSI-RS is used by the first UE toperform layer 3 (L3) CSI-RS mobility measurements.
 13. The base stationof claim 12, wherein the base station does not indicate pre-emption tothe first UE and the second configuration is the first configuration.14. The base station of claim 12, wherein the second configurationincludes a zero-power CSI-RS (ZP-CSI-RS) as the L3 CSI-RS.
 15. The basestation of claim 12, wherein the operations further comprise: applying ascheduling restriction to the first UE on the symbol.
 16. The basestation of claim 15, wherein the scheduling restriction comprises notscheduling control or data transmissions to the first UE on the symbol.17. The base station of claim 16, wherein the not scheduling the datatransmissions comprises not scheduling Physical Downlink Control Channel(PDSCH) transmissions.
 18. The base station of claim 15, wherein theoperations further comprise: applying a scheduling restriction to thesecond UE on the symbol.
 19. A processor of a first user equipment (UE)configured to perform operations comprising: receiving, from a basestation of a network, a first configuration for a channel stateinformation reference signal (CSI-RS) on a symbol, wherein the CSI-RS isused by the first UE to perform layer 3 (L3) CSI-RS mobilitymeasurements and wherein a data transmission for a second UE is alsoscheduled on the symbol; and receiving, from the base station, ascheduling restriction for the symbol.
 20. The processor of claim 19,wherein the scheduling restriction comprises the UE not being scheduledfor control or data transmissions on the symbol.
 21. The processor ofclaim 20, wherein the first UE is in an enhanced mobile broadband (eMBB)configuration with the base station and the second UE is in an ultrareliable low latency communications (URLLC) configuration with the basestation.